Conversation
kkafar
marked this pull request as draft
October 22, 2025 13:39
kkafar
force-pushed
the
@kkafar/align-prop-naming-auto
branch
from
January 16, 2026 12:43
3013eb4 to
446da5d
Compare
Member
Author
|
It stays as is screens for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR aligns property naming in "gamma" components between platforms. Indeed it does not make sense to have part of the enum values called
autoand partautomatic, e.g.TabBarMinimizeBehavior::automatic&TabBarItemLabelVisibilityMode::auto.Since these are new APIs we can have it nicely aligned on stable release.
I've decided to go withautoin favour ofautomaticbecause it is shorter and clearly conveys the meaning.To be honest I can't decide. There is no consistency neither in the world nor in our API.
I've done a quick research and we have in
react-native-screens:TabBarItemLabelVisibilityMode::auto(Android, not-yet-stable API)ScreenProps::statusBarStyle::auto(Android, iOS, stable API)TabBarControllerMode::automatic(iOS, not-yet-stable API)TabBarMinimizeBehavior::automatic(iOS, not-yet-stable API)ScrollEdgeEffect::automatic(iOS, stable API)SearchBarPlacement::automatic(iOS, stable API)SplitBehavior::automatic(iOS, not-yet-stable API)SplitDisplayMode::automatic(iOS, not-yet-stable API)SplitDisplayModeButtonVisibility::automatic(iOS, not-yet-stable API)Then in
react-native:ScrollView::overScrollMode::auto(Android, RN API)Image::resizeMethod::auto(Android, RN API)TextInput::importantForAutoFill::auto(Android, RN API)View::importantForAccessibility::auto(Android, RN API)View::pointerEvents::auto(RN API)autoautoautoScrollView::contentInsetAdjustmentBehavior::automatic(ScrollView public API)Additionally many iOS props such as
ScrollView::automaticallyAdjustContentInsetsuse theautomatic.The dividing line here is clearly the platform.
And it seems that the convention in react-native is to stick to the platform conventions.
Changes
This PR renames exactly:
TabBarMinimizeBehavior::automatic->TabBarMinimizeBehavior::autoTabBarControllerMode::automatic->TabBarControllerMode::autoautomatic->autoto align between platformsTest code and steps to reproduce
Checklist